Is there any release date for the support of PSM and eDRX features? If you cant keep up with the amount of work you have to deliver, maybe you should think something like bounties for most requested features by your community.

@xykon thanks for this note. In this case I didn't need to reflash the firmware, however I will remember your advice as I am sure to need it soon enough!

Hi guys, After done some test I realize that the GPY only exist from deepsleep if is power with 5V. If I power the GYP with 3.5V it hangs forever in deepsleep. This is normal? Cumps,

@jmarcelino I'm getting the following error: Traceback (most recent call last): File "main.py", line 13, in <module> AttributeError: 'RTC' object has no attribute 'irq' MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32 Type "help()" for more information.

@cssmacs01 just use the native machine.deepsleep and related functions: https://docs.pycom.io/chapter/firmwareapi/pycom/machine/#machinedeepsleeptimems The deep sleep shield and other workarounds are only needed for some of the modules, the FiPy is not one of them.

@toppert Some of power banks can support low current mode. Some of tem must be turned in this mode by special press on the button, some work from the start. But many do not support low current mode at all. E.g. "Mi" power banks support this mode - but as @seb say already it is super inefficient. You can got longer time from battery then from powerbanks.

@marcobenini @marcobenini said in Avoid LoPy to restart after deep sleep: @seb Thenk You for the useful link. There could potentially a problem with lora.nvram_save() and fast memory wear due to too high writes or I am wrong? For example: if the NVS (flash memory) is a 100k write cycles unit, use deep sleep and if I send a message every 2 minutes, than in about 140 days the 100k writes is reached. From my understanding of the esp32 forum thread linked previously the NVS is wear leveled so depending on the amount of data it would last longer but for such frequent writes, I would recommend either an SD card or some sort of external RAM that remains powered. Maybe some parameters could not be re-written, but some, like packets counters change every time a LoRa message is sent. There are functions in the firmware for this already: https://docs.pycom.io/chapter/firmwareapi/pycom/network/lora.html#loranvramsave but these also use NVS, this should only need to be done when the device is going into and out of sleep Will Pycom change the functions also to include external memory (for example I2C / SPI FRAM, ...)? There are no plans to do this at the moment, but this doesnt prevent you from adding it yourself for your application. Could the parameters that change be transferred to the microcontroller used for sleep control? I'm afraid the memory on this microcontroller is already running tight, I doubt this could be added. In LoPy4 how are managed the LoRa parameters, does them remain stored in the Semtech LoRa chip? See above I ask since I looking to put together a solution for a test project which end devices have to be battery power, collect data, but send periodically to save power.

Sorry, I misunderstood. I can only tell you that the Pygate mounting hole spacing is the same as the Expansionboard 3.0's spacing. We provide that here: https://docs.pycom.io/gitbook/assets/specsheets/Pycom_002_Specsheets_Pygate_v1.pdf in section 12. I will work on getting the Expansionboard spacing out there on its own page!

@arno Unfortunately the deepsleep shield does not have any such functionality

This error statement TypeError: 'module' object is not callable is raised as you are being confused about the Class name and Module name. The problem is in the import line . You are importing a module, not a class. This happend because the module name and class name have the same name . If you have a class "MyClass" in a file called "MyClass.py" , then you should import : from MyClass import MyClass In Python , a script is a module, whose name is determined by the filename . So when you start out your file MyClass.py with import MyClass you are creating a loop in the module structure. In Python, everything (including functions, methods, modules, classes etc.) is an object , and methods are just attributes like every others. So,there's no separate namespaces for methods. So when you set an instance attribute, it shadows the class attribute by the same name. The obvious solution is to give attributes different names.

@jcaron Thanks. Just to note this method works also for both a software reset AND powercycle.

@jmarcelino Thanks

@fsergeys You should measure power draw from battery, not USB. There's a lot more going on when powered via USB, it's not representative of what happens when you're running on battery. You can definitely use the Pytrack's deep sleep (use the PyTrack library) to power down completely the WiPy, but you shouldn't see much of a difference when running from battery in the case of a WiPy 3.

@fred said in When is the Deep Sleep Shield required?: Ultra Low Power mode is available on the devices straight out of the box. It's probably also worth mentioning that it doesn't work...

@gruia-nichita You don’t need the deep sleep shield on the Pysense/Pytrack, that functionality is built in.

You can get the wake reason using ds.get_wake_status(). I think the default is that there are no other wake-up sources configured, but you may try to disable_wake_on_fall(['P10','P17', 'P18']) and disable_wake_on_raise(['P10','P17', 'P18']) just to be sure. Full details here: https://docs.pycom.io/chapter/datasheets/boards/deepsleep/api.html

It is indeed mentioned in this post. So I'll be able to get rid of the expansion board but not the deep sleep shield for it to be fully efficient That's exactly what I was thinking but I wanted to be sure about especially about the current since it worked but I was sure there will still be current consumption problems without the shield. Thank you for your fast reply, this will reduce the size of my project.

@reidfo I use the boot.py to mount the SD card just once. When I mounted the SD card in the main.py I encountered OSError when re-running my code in the REPL (OSError: the requested operation is not possible) due to the fact that I cannot check the status of the SD card.